Errors found while checking this document as XHTML 1.0 Strict!

Result: 136 Errors, 15 warning(s)
:
: utf-8
: XHTML 1.0 Strict
Root Element: html
Options

Help on the options is available.

↑ Top

Validation Output: 136 Errors

  1. Error Line 1, Column 146: Attribute "class" exists, but can not be used for this element.
    …<html lang="en" xml:lang="en" class="en" xmlns:fb="http://www.facebook.com/20

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  2. Error Line 1, Column 110: Missing xmlns attribute for element html. The value should be: http://www.w3.org/1999/xhtml
    …rg/TR/xhtml1/DTD/xhtml1-strict.dtd"><html lang="en" xml:lang="en" class="en" 

    Many Document Types based on XML need a mandatory xmlns="" on the root element. For example, the root element for XHTML will look like:
    <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">

  3. Error Line 7, Column 70: element "esi:vars" undefined
    …ico" rel="shortcut icon" /><esi:vars><script type="text/javascript">var spons

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  4. Error Line 7, Column 251: syntax of attribute value does not conform to declared value
    …/script></esi:vars></head><body id=""><div id="ThirdPartyTrackers"><script ty

    The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

  5. Error Line 7, Column 1486: Attribute "target" exists, but can not be used for this element.
    …<a href="http://ca.msn.com/" target="_blank"><img src="/img/template/poweredb

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  6. Error Line 7, Column 1568: required attribute "alt" not specified
    …_logo.jpg" width="130" height="40" /></a><a href="/get-games-ready/index.html

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  7. Error Line 7, Column 1708: required attribute "alt" not specified
    …r_logo.jpg" width="95" height="25" /></a></div><div id="ctvo_SearchForm"><div

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  8. Error Line 7, Column 2298: Attribute "language" exists, but can not be used for this element.
    …s=''"> </div></div><script language="javascript" type="text/javascript">Manag

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  9. Error Line 10, Column 132: Attribute "size" exists, but can not be used for this element.
    …"display:none"><fb:profile-pic size="square" width="21px" height="21px" faceb

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  10. Error Line 10, Column 147: Attribute "width" exists, but can not be used for this element.
    …<fb:profile-pic size="square" width="21px" height="21px" facebook-logo="true"

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  11. Error Line 10, Column 161: Attribute "height" exists, but can not be used for this element.
    …c size="square" width="21px" height="21px" facebook-logo="true" uid="loggedin

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  12. Error Line 10, Column 182: Attribute "facebook-logo" is not a valid attribute
    …="21px" height="21px" facebook-logo="true" uid="loggedinuser" linked="false">

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  13. Error Line 10, Column 193: Attribute "uid" is not a valid attribute. Did you mean "http-equiv" or "width"?
    …ght="21px" facebook-logo="true" uid="loggedinuser" linked="false"> </fb:profi

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  14. Error Line 10, Column 215: Attribute "linked" is not a valid attribute. Did you mean "vlink" or "alink"?
    …go="true" uid="loggedinuser" linked="false"> </fb:profile-pic></div><div id="

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  15. Error Line 10, Column 222: element "fb:profile-pic" undefined
    …e" uid="loggedinuser" linked="false"> </fb:profile-pic></div><div id="fb_favi

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  16. Error Line 10, Column 302: Attribute "background" exists, but can not be used for this element.
    …_login"><fb:login-button background="dark" onlogin="FBConnect.OnLogin();" siz

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  17. Error Line 10, Column 317: Attribute "onlogin" is not a valid attribute. Did you mean "scrolling" or "onload"?
    …in-button background="dark" onlogin="FBConnect.OnLogin();" size="medium" leng

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  18. Error Line 10, Column 345: Attribute "size" exists, but can not be used for this element.
    …onlogin="FBConnect.OnLogin();" size="medium" length="short"> </fb:login-butto

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  19. Error Line 10, Column 361: Attribute "length" is not a valid attribute. Did you mean "maxlength" or "content"?
    …ct.OnLogin();" size="medium" length="short"> </fb:login-button></div><script 

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  20. Error Line 10, Column 368: element "fb:login-button" undefined
    …gin();" size="medium" length="short"> </fb:login-button></div><script type="t

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  21. Error Line 13, Column 176: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ext-align:center;font-color:#AA1B31'><strong><a href='http://get.adobe.com/fl

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  22. Error Line 17, Column 189: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …0x90;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/c

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  23. Error Line 19, Column 189: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …0x90;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/c

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  24. Error Line 21, Column 189: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …0x90;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/c

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  25. Error Line 24, Column 324: required attribute "action" not specified
    …hortCut"><form id="ctvo_FormChoices"><div class="" onmouseover="$(this).addCl

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  26. Error Line 24, Column 1438: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …lick="myMenu.saveComboShortcuts()" /><input style="display:none" type="button

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  27. Error Line 24, Column 1549: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ndo" onclick="myMenu.undoChoice()" /><input style="display:none" type="button

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  28. Error Line 24, Column 1663: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …et" onclick="myMenu.resetChoice()" /></form></div></div> </div></div><script 

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  29. Error Line 46, Column 111: value of attribute "id" invalid: "1" cannot start a name
    …floatLeft "><div class="hslice "id="1">

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  30. Error Line 50, Column 120: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ext-align:center;font-color:#AA1B31'><strong><a href='http://get.adobe.com/fl

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  31. Warning Line 51, Column 267: reference not terminated by REFC delimiter
    …ewsreaderconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=fals

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  32. Warning Line 51, Column 270: cannot generate system identifier for general entity "environment"
    …readerconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=false',

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  33. Error Line 51, Column 270: general entity "environment" not defined and no default entity
    …readerconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=false',

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  34. Warning Line 51, Column 281: reference not terminated by REFC delimiter
    …g/Config_home.xml&lang=E&environment=2&test=1&target_blank=false','flash38775

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  35. Error Line 51, Column 281: reference to entity "environment" for which no system identifier could be generated
    …g/Config_home.xml&lang=E&environment=2&test=1&target_blank=false','flash38775

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  36. Info Line 51, Column 268: entity was defined here
    …wsreaderconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=false
  37. Warning Line 51, Column 284: cannot generate system identifier for general entity "test"
    …onfig_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  38. Error Line 51, Column 284: general entity "test" not defined and no default entity
    …onfig_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  39. Warning Line 51, Column 288: reference not terminated by REFC delimiter
    …g_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b0

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  40. Error Line 51, Column 288: reference to entity "test" for which no system identifier could be generated
    …g_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b0

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  41. Info Line 51, Column 282: entity was defined here
    …/Config_home.xml&lang=E&environment=2&test=1&target_blank=false','flash387755
  42. Warning Line 51, Column 291: cannot generate system identifier for general entity "target_blank"
    …ome.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b04f2

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  43. Error Line 51, Column 291: general entity "target_blank" not defined and no default entity
    …ome.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b04f2

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  44. Warning Line 51, Column 303: reference not terminated by REFC delimiter
    …=E&environment=2&test=1&target_blank=false','flash3877558a61b04f23b7d7c94932d

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  45. Error Line 51, Column 303: reference to entity "target_blank" for which no system identifier could be generated
    …=E&environment=2&test=1&target_blank=false','flash3877558a61b04f23b7d7c94932d

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  46. Info Line 51, Column 289: entity was defined here
    …_home.xml&lang=E&environment=2&test=1&target_blank=false','flash3877558a61b04
  47. Error Line 54, Column 148: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ext-align:center;font-color:#AA1B31'><strong><a href='http://get.adobe.com/fl

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  48. Error Line 56, Column 305: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …ext-align:center;font-color:#AA1B31'><strong><a href='http://get.adobe.com/fl

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  49. Warning Line 57, Column 386: reference not terminated by REFC delimiter
    …eatured_photogalleries_home.xml&lang=E&environment=2&test=1','flashf26fe2258d

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  50. Warning Line 57, Column 400: reference not terminated by REFC delimiter
    …alleries_home.xml&lang=E&environment=2&test=1','flashf26fe2258d51435c8a85e1cf

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  51. Error Line 57, Column 400: reference to entity "environment" for which no system identifier could be generated
    …alleries_home.xml&lang=E&environment=2&test=1','flashf26fe2258d51435c8a85e1cf

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  52. Info Line 51, Column 268: entity was defined here
    …wsreaderconfig/Config_home.xml&lang=E&environment=2&test=1&target_blank=false
  53. Warning Line 57, Column 407: reference not terminated by REFC delimiter
    …s_home.xml&lang=E&environment=2&test=1','flashf26fe2258d51435c8a85e1cf01507da

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  54. Error Line 57, Column 407: reference to entity "test" for which no system identifier could be generated
    …s_home.xml&lang=E&environment=2&test=1','flashf26fe2258d51435c8a85e1cf01507da

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  55. Info Line 51, Column 282: entity was defined here
    …/Config_home.xml&lang=E&environment=2&test=1&target_blank=false','flash387755
  56. Error Line 58, Column 3353: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  57. Error Line 58, Column 4478: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  58. Error Line 58, Column 6016: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  59. Error Line 58, Column 7147: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  60. Error Line 58, Column 8696: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  61. Error Line 58, Column 9821: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  62. Error Line 58, Column 11357: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  63. Error Line 58, Column 12456: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  64. Error Line 58, Column 13941: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  65. Error Line 58, Column 15045: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  66. Error Line 58, Column 16535: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  67. Error Line 58, Column 17629: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  68. Error Line 58, Column 19101: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  69. Error Line 58, Column 20227: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  70. Error Line 58, Column 21775: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  71. Error Line 58, Column 22903: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  72. Error Line 58, Column 24448: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  73. Error Line 58, Column 25560: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  74. Error Line 58, Column 27075: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  75. Error Line 58, Column 28184: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  76. Error Line 58, Column 29697: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  77. Error Line 58, Column 30813: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  78. Error Line 58, Column 32331: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  79. Error Line 58, Column 33442: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …a/index.html"><div class="ctvo_flag"><img src="/imgml/flags/roundedFlags/37x3

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  80. Error Line 58, Column 34782: Attribute "widht" is not a valid attribute. Did you mean "width" or "marginwidth"?
    …ow_dx.png" alt="" height="22" widht="18" style="cursor: pointer;" /> </div><s

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  81. Error Line 67, Column 174: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …x250;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/c

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  82. Warning Line 68, Column 108: character "&amp;" is the first character of a delimiter but occurred as data
    …lass="ctvo_titleLeft"> </span>Blogs & Features<span class="ctvo_titleRight"> 

    This message may appear in several cases:

    • You tried to include the "<" character in your page: you should escape it as "&lt;"
    • You used an unescaped ampersand "&": this may be valid in some contexts, but it is recommended to use "&amp;", which is always safe.
    • Another possibility is that you forgot to close quotes in a previous tag.
  83. Error Line 68, Column 1481: element "BR" undefined. Did you mean "br"?
    …medal to be won on Canadian soil.<BR> </div> </div> </div>  </div><div class=

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  84. Error Line 68, Column 1488: end tag for "BR" omitted, but OMITTAG NO was specified
    …o be won on Canadian soil.<BR> </div> </div> </div>  </div><div class="ctvo_b

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  85. Info Line 68, Column 1477: start tag was here
    …old medal to be won on Canadian soil.<BR> </div> </div> </div>  </div><div cl
  86. Error Line 68, Column 3361: element "P" undefined. Did you mean "p"?
    …e comes the sun </strong></a></h3><P>The clouds finally parted, literally,&nb

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  87. Error Line 73, Column 728: end tag for "br" omitted, but OMITTAG NO was specified
    … and A to find your hockey twin.<br> </div></li><li><a href="http://call.ctvo

    You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

  88. Info Line 73, Column 723: start tag was here
    …ive Q and A to find your hockey twin.<br> </div></li><li><a href="http://call
  89. Error Line 75, Column 126: required attribute "type" not specified
    …"><div class=""><div class=""><style>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  90. Error Line 75, Column 126: document type does not allow element "style" here
    …"><div class=""><div class=""><style>

    The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

    One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

  91. Error Line 103, Column 261: required attribute "alt" not specified
    …Games.jpg" width="163" height="95" /> </a> </div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  92. Error Line 104, Column 242: required attribute "alt" not specified
    …ockey.jpg" width="163" height="95" /> </a> </div>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  93. Error Line 106, Column 99: value of attribute "id" invalid: "2" cannot start a name
    …="ctvo_box"><div class="hslice" id="2"><a rel="feedurl" href="/webslices/libr

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  94. Error Line 133, Column 745: required attribute "alt" not specified
    …/videopage/GetSirverlight_326.jpg" /></a></div><div class="with_background"><

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  95. Error Line 133, Column 1132: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …Text();"><div class="ctvo_thumbCntr"><img src="/mm//Photo/Generic/General/04/

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  96. Error Line 133, Column 1662: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …Text();"><div class="ctvo_thumbCntr"><img src="/mm//Photo/Sports/Events/04/17

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  97. Error Line 133, Column 2216: document type does not allow element "div" here; missing one of "object", "ins", "del", "map", "button" start-tag
    …Text();"><div class="ctvo_thumbCntr"><img src="/mm//Photo/Sports/Events/04/17

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  98. Error Line 133, Column 2616: required attribute "alt" not specified
    …mgml/follow.jpg" class="nextVideo" /></a> </div><div class="ctvo_videotext"><

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  99. Error Line 137, Column 174: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …x250;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/c

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  100. Error Line 137, Column 736: Attribute "name" exists, but can not be used for this element.
    …nswers"><form id="f_poll41606" name="f_poll41606"><ul class="PollQAList"><li>

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  101. Error Line 137, Column 749: required attribute "action" not specified
    … id="f_poll41606" name="f_poll41606"><ul class="PollQAList"><li><input class=

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  102. Error Line 137, Column 838: value of attribute "id" invalid: "5" cannot start a name
    …" type="radio" name="i_answers" id="502" value="502" /><label for="502">Yes <

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  103. Error Line 137, Column 869: value of attribute "for" invalid: "5" cannot start a name
    … id="502" value="502" /><label for="502">Yes </label></li><li class="Last"><i

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  104. Error Line 137, Column 969: value of attribute "id" invalid: "5" cannot start a name
    …" type="radio" name="i_answers" id="503" value="503" /><label for="503">No </

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  105. Error Line 137, Column 1000: value of attribute "for" invalid: "5" cannot start a name
    … id="503" value="503" /><label for="503">No </label></li></ul><input type="bu

    It is possible that you violated the naming convention for this attribute. For example, id and name attributes must begin with a letter, not a digit.

  106. Error Line 137, Column 1202: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …okie.setRaw('poll41606',41606,30)" /><input type="hidden" value="Please choos

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  107. Error Line 137, Column 1285: document type does not allow element "input" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …ption" id="message" name="message" /><esi:vars><input type="hidden" name="geo

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  108. Error Line 137, Column 1295: element "esi:vars" undefined
    …"message" name="message" /><esi:vars><input type="hidden" name="geo_country" 

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  109. Warning Line 142, Column 105: cannot generate system identifier for general entity "ThanksUrl"
    …lack.html?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  110. Error Line 142, Column 105: general entity "ThanksUrl" not defined and no default entity
    …lack.html?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  111. Warning Line 142, Column 114: reference not terminated by REFC delimiter
    …?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{metho

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  112. Error Line 142, Column 114: reference to entity "ThanksUrl" for which no system identifier could be generated
    …?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{metho

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  113. Info Line 142, Column 103: entity was defined here
    …tBlack.html?ThanksText='+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.rand
  114. Warning Line 142, Column 129: cannot generate system identifier for general entity "rnd"
    …hanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$('r

    An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in "Ampersands in URLs".

    Entity references start with an ampersand (&) and end with a semicolon (;). If you want to use a literal ampersand in your document you must encode it as "&amp;" (even inside URLs!). Be careful to end entity references with a semicolon or your entity reference may get interpreted in connection with the following text. Also keep in mind that named entity references are case-sensitive; &Aelig; and &aelig; are different characters.

    If this error appears in some markup generated by PHP's session handling code, this article has explanations and solutions to your problem.

    Note that in most documents, errors related to entity references will trigger up to 5 separate messages from the Validator. Usually these will all disappear when the original problem is fixed.

  115. Error Line 142, Column 129: general entity "rnd" not defined and no default entity
    …hanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$('r

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  116. Warning Line 142, Column 132: reference not terminated by REFC delimiter
    …ksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$('resu

    If you meant to include an entity that starts with "&", then you should terminate it with ";". Another reason for this error message is that you inadvertently created an entity by failing to escape an "&" character just before this text.

  117. Error Line 142, Column 132: reference to entity "rnd" for which no system identifier could be generated
    …ksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$('resu

    This is usually a cascading error caused by a an undefined entity reference or use of an unencoded ampersand (&) in an URL or body text. See the previous message for further details.

  118. Info Line 142, Column 127: entity was defined here
    …+ThanksText+'&ThanksUrl='+ThanksUrl+'&rnd='+Math.random(),{method: 'get'});$(
  119. Error Line 145, Column 174: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …x100;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/c

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  120. Error Line 148, Column 321: Attribute "class" exists, but can not be used for this element.
    …div class="fb_fanbox"><fb:fan class="FBFanWidgetSmall" profile_id="9161952952

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  121. Error Line 148, Column 351: Attribute "profile_id" is not a valid attribute. Did you mean "profile"?
    …class="FBFanWidgetSmall" profile_id="91619529529" stream="0" connections="5" 

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  122. Error Line 148, Column 372: Attribute "stream" is not a valid attribute. Did you mean "scheme" or "frameborder"?
    …ll" profile_id="91619529529" stream="0" connections="5" width="326" height="1

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  123. Error Line 148, Column 388: Attribute "connections" is not a valid attribute
    …91619529529" stream="0" connections="5" width="326" height="165"> </fb:fan> <

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  124. Error Line 148, Column 398: Attribute "width" exists, but can not be used for this element.
    …9" stream="0" connections="5" width="326" height="165"> </fb:fan> </div><div 

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  125. Error Line 148, Column 411: Attribute "height" exists, but can not be used for this element.
    … connections="5" width="326" height="165"> </fb:fan> </div><div class="fb_fan

    You have used the attribute named above in your document, but the document type you are using does not support that attribute for this element. This error is often caused by incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Transitional" document type to get the "target" attribute), or by using vendor proprietary extensions such as "marginheight" (this is usually fixed by using CSS to achieve the desired effect instead).

    This error may also result if the element itself is not supported in the document type you are using, as an undefined element will have no supported attributes; in this case, see the element-undefined error message for further information.

    How to fix: check the spelling and case of the element and attribute, (Remember XHTML is all lower-case) and/or check that they are both allowed in the chosen document type, and/or use CSS instead of this attribute. If you received this error when using the <embed> element to incorporate flash media in a Web page, see the FAQ item on valid flash.

  126. Error Line 148, Column 416: element "fb:fan" undefined
    …ections="5" width="326" height="165"> </fb:fan> </div><div class="fb_fanfoote

    You have used the element named above in your document, but the document type you are using does not define an element of that name. This error is often caused by:

    • incorrect use of the "Strict" document type with a document that uses frames (e.g. you must use the "Frameset" document type to get the "<frameset>" element),
    • by using vendor proprietary extensions such as "<spacer>" or "<marquee>" (this is usually fixed by using CSS to achieve the desired effect instead).
    • by using upper-case tags in XHTML (in XHTML attributes and elements must be all lower-case).
  127. Error Line 153, Column 174: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …x100;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/c

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  128. Error Line 155, Column 174: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …x100;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/c

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  129. Error Line 157, Column 174: document type does not allow element "a" here; missing one of "p", "h1", "h2", "h3", "h4", "h5", "h6", "div", "pre", "address", "fieldset", "ins", "del" start-tag
    …x100;ord=123456789?" target="_blank"><img src="http://ad.doubleclick.net/ad/c

    The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

    One possible cause for this message is that you have attempted to put a block-level element (such as "<p>" or "<table>") inside an inline element (such as "<a>", "<span>", or "<font>").

  130. Error Line 157, Column 431: required attribute "type" not specified
    …-><div id="ctvo_ctvCurrUrlP"><script>

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  131. Error Line 162, Column 221: ID "m1curling" already defined
    …>Figure Skating</a></span><span id="m1curling"><a href="/curling/index.html">

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  132. Info Line 23, Column 194: ID "m1curling" first defined here
    …"ctvo_first ">Hockey</a></li><li id="m1curling"><a href="/curling/index.html"
  133. Error Line 162, Column 290: ID "m1hockey" already defined
    …x.html">Curling</a></span><span id="m1hockey"><a href="/hockey/index.html">Ho

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  134. Info Line 23, Column 112: ID "m1hockey" first defined here
    …vel1Menu"><li class="ctvo_first" id="m1hockey"><a href="/hockey/index.html" c
  135. Error Line 162, Column 379: ID "m1snowboard" already defined
    …an></div><div class="row"><span id="m1snowboard"><a href="/snowboard/index.ht

    An "id" is a unique identifier. Each time this attribute is used in a document it must have a different value. If you are using this attribute as a hook for style sheets it may be more appropriate to use classes (which group elements) than id (which are used to identify exactly one element).

  136. Info Line 23, Column 1573: ID "m1snowboard" first defined here
    …g </a></li> </ul> </div></li><li id="m1snowboard"><a href="/snowboard/index.h
  137. Error Line 163, Column 5514: required attribute "alt" not specified
    …imgml/template/ms_footer_2010.gif" /></div></div><script type="text/javascrip

    The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.

    Typical values for type are type="text/css" for <style> and type="text/javascript" for <script>.

  138. Error Line 46, Column > 80: XML Parsing Error: attributes construct error
    …iv class="ctvo_masterCol8 ctvo_floatLeft "><div class="hslice "id="1">…

  139. Error Line 46, Column > 80: XML Parsing Error: Couldn't find end of Start Tag div line 46
    …iv class="ctvo_masterCol8 ctvo_floatLeft "><div class="hslice "id="1">…

  140. Error Line 47, Column 23: XML Parsing Error: attributes construct error
    <h2 class="entry-title"style="display:none">Headlines</h2>

  141. Error Line 47, Column 23: XML Parsing Error: Couldn't find end of Start Tag h2 line 47
    <h2 class="entry-title"style="display:none">Headlines</h2>

  142. Error Line 47, Column 58: XML Parsing Error: Opening and ending tag mismatch: div line 46 and h2
    <h2 class="entry-title"style="display:none">Headlines</h2>

  143. Error Line 49, Column 55: XML Parsing Error: attributes construct error
    <a href="/webslices/library/_bridgePage_headlines.html"rel="feedurl"> </a>

  144. Error Line 49, Column 55: XML Parsing Error: Couldn't find end of Start Tag a line 49
    <a href="/webslices/library/_bridgePage_headlines.html"rel="feedurl"> </a>

  145. Error Line 49, Column 74: XML Parsing Error: Opening and ending tag mismatch: div line 48 and a
    …idgePage_headlines.html"rel="feedurl"> </a>

  146. Error Line 51, Column > 80: XML Parsing Error: EntityRef: expecting ';'
    …gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s…

  147. Error Line 51, Column > 80: XML Parsing Error: EntityRef: expecting ';'
    …gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s…

  148. Error Line 51, Column > 80: XML Parsing Error: EntityRef: expecting ';'
    …gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s…

  149. Error Line 51, Column > 80: XML Parsing Error: EntityRef: expecting ';'
    …gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s…

  150. Error Line 57, Column > 80: XML Parsing Error: EntityRef: expecting ';'
    …gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s…

  151. Error Line 57, Column > 80: XML Parsing Error: EntityRef: expecting ';'
    …gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s…

  152. Error Line 57, Column > 80: XML Parsing Error: EntityRef: expecting ';'
    …gin.<br /><img src='/imgml/get_flash_player.gif' alt='Flash Player' /></a></s…

  153. Error Line 68, Column > 80: XML Parsing Error: xmlParseEntityRef: no name
    …class="ctvo_box"><h2><span class="ctvo_titleLeft"> </span>Blogs & Features<sp…

  154. Error Line 68, Column > 80: XML Parsing Error: Opening and ending tag mismatch: BR line 68 and div
    …class="ctvo_box"><h2><span class="ctvo_titleLeft"> </span>Blogs & Features<sp…

  155. Error Line 73, Column > 80: XML Parsing Error: Opening and ending tag mismatch: br line 73 and div
    …4"><div class="ctvo_box"><div class="ctvo_PreviewNews"><h2><span class="ctvo_…

  156. Error Line 73, Column > 80: XML Parsing Error: Opening and ending tag mismatch: div line 73 and li
    …4"><div class="ctvo_box"><div class="ctvo_PreviewNews"><h2><span class="ctvo_…

  157. Error Line 73, Column > 80: XML Parsing Error: Opening and ending tag mismatch: li line 73 and ul
    …4"><div class="ctvo_box"><div class="ctvo_PreviewNews"><h2><span class="ctvo_…

  158. Error Line 73, Column > 80: XML Parsing Error: Opening and ending tag mismatch: ul line 73 and div
    …4"><div class="ctvo_box"><div class="ctvo_PreviewNews"><h2><span class="ctvo_…

  159. Error Line 142, Column > 80: XML Parsing Error: EntityRef: expecting ';'
    …lls/pollid='+id+'/resultBlack.html?ThanksText='+ThanksText+'&ThanksUrl='+Than…

  160. Error Line 142, Column > 80: XML Parsing Error: EntityRef: expecting ';'
    …lls/pollid='+id+'/resultBlack.html?ThanksText='+ThanksText+'&ThanksUrl='+Than…

  161. Error Line 186, Column 6: XML Parsing Error: Opening and ending tag mismatch: body line 7 and div
    </div></body></html>

  162. Error Line 186, Column 13: XML Parsing Error: Opening and ending tag mismatch: html line 1 and body
    </div></body></html>

  163. Error Line 186, Column 13: XML Parsing Error: Extra content at the end of the document
    </div></body></html>

↑ Top